Skip to content

Conversation

@manish-agrawal-ai
Copy link
Contributor

@manish-agrawal-ai manish-agrawal-ai commented Nov 11, 2022

Description

Saving Resource status while installing any integrations and returning these resources in get module info call

Fixes #2582

How Has This Been Tested?

  • Installing integrations - check the DB (integration which has label set in central-api, and integration which does have label set in central-api)
  • module info API is returning integrations resources status

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates? NO
  • I've updated documentation as required by this PR. NA
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


@manish-agrawal-ai manish-agrawal-ai changed the title Issue 2582 feat: Resource status for integration Nov 15, 2022
@gitguardian
Copy link

gitguardian bot commented Nov 29, 2022

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id Secret Commit Filename
141558 Generic High Entropy Secret 60e284b scripts/devtron-reference-helm-charts/reference-chart_4-16-0/env-values.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

vikramdevtron
vikramdevtron previously approved these changes Dec 2, 2022
@vikramdevtron vikramdevtron self-requested a review December 14, 2022 09:39
@manish-agrawal-ai manish-agrawal-ai merged commit f07f89e into main Dec 14, 2022
@manish-agrawal-ai manish-agrawal-ai deleted the issue_2582 branch December 14, 2022 11:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Make Integration installation success condition independent of devtron helm release and need debugging during Integration installation

3 participants